Automate Astro Deployments with Sanity and Vercel

1 min read July 14, 2026

Without automation, every time you publish new content in Sanity you need to manually redeploy your project in Vercel before visitors can see the changes.

By connecting Sanity Webhooks with a Vercel Deploy Hook, every published article automatically triggers a new deployment. Your content goes live without any manual work.

Why This Setup Matters

Publish articles without logging into Vercel.
Keep your live website always up to date.
Eliminate forgotten manual deployments.
Perfect for content editors who only use Sanity Studio.
Keep the speed and SEO benefits of a static Astro website.

How It Works

An editor publishes content in Sanity Studio.
Sanity sends a webhook after the content is published.
Vercel receives the webhook through a Deploy Hook.
Vercel rebuilds the Astro site.
The updated website is automatically published.

The entire process usually completes within a minute or two.

Frequently asked questions

Why doesn't my Astro website update immediately after publishing?

Most Astro websites are statically generated. Content is fetched during the build process, so publishing new content in Sanity does not automatically update the live website. A new build is required.

What is a Vercel Deploy Hook?

A Deploy Hook is a secure URL provided by Vercel that starts a new deployment when it receives an HTTP POST request. It allows external services, such as Sanity, to trigger deployments automatically.

What is a Sanity Webhook?

A Sanity Webhook sends a notification whenever selected content changes. By configuring it to trigger on published articles, it can automatically start a new deployment in Vercel.

Will every draft trigger a deployment?

No. Configure the webhook to listen only to published documents (or exclude drafts with a GROQ filter). This prevents unnecessary builds while you're editing content.

Does this affect my website's performance?

No. Your website remains a static Astro site with all the performance and SEO benefits. The only difference is that deployments happen automatically after publishing.

Is this setup better than switching to server-side rendering?

For most blogs and marketing websites, yes. Static Astro sites are faster, cheaper to host, and easier to cache. Automatic deployments provide fresh content without sacrificing performance.

How long does it take for changes to appear?

Typically between 30 seconds and 2 minutes, depending on your Vercel build time. Once the deployment finishes, your new content is live automatically.

Can I trigger deployments only for articles?

Yes. Use a GROQ filter such as: _type == "article"